Agile

Optimal lifecycle when deliverable frequency is high and anticipated change is high.

Blockers

Issues or problems preventing a development team from progressing in a Sprint.

Burndown Chart

Information Radiator that graphically shows team progress to complete User Stories.

Ceremonies

Events to include sprint planning, the Sprint, reviews and retrospectives.

Coach

Process conducted to improve team member performance and confidence.

Crystal

An agile methodology that is an agile framework which puts focus on the interaction among individuals rather than on the processes and tools used.

Daily Scrum/Daily Stand-up meeting

A Scrum ceremony conducted for 15-minutes each day to ensure the Sprint is progressing and identify any potential blockers.

Done

Done is realized when all solution criteria for a User Story is accomplished to the customer's satisfaction.

Development Team

Team members committed to creating useable increments during each Sprint.

Diversion Shield

Shield the team from external distractions. Create an environment where the team can focus on the job at hand.

DSDM

Dynamic Systems Development Method. An agile project delivery framework initially used as a software development method.

Dysfunctional Conflict

Conflict that can lead to negative feelings and results.

Empirical Process Control

Promote transparency, ensure inspections occur as needed, and work with the team to adapt to change.

Extreme Programming (XP)

A software development methodology intended to improve software quality and responsiveness to changing customer requirements.

Facilitate

Lead communications and collaboration to achieve an outcome.

Functional Conflict

Conflict that can lead to positive feelings and results.

Impediments

Issues or problems preventing a development team from progressing in a Sprint.

Information Radiators

Forms of agile communications that are transparent and available to all stakeholders.

Kanban Board

A tool used to display all backlog tasks in a Sprint and status.

Lean Software Development (LSD)

An agile framework based on optimizing development time and resources, eliminating waste, and ultimately delivering only what the product needs.

MVP

Minimum Viable Product. The product increment developed during a given Sprint. The increment must have value to the customer.

Predictive

Lifecycle where project scope, schedules, and budgets are determined early in a project. Best if delivery requirements are low and change is low.

Product Backlog

A repository of prioritized User Stories developed and managed by a Product Owner.

Product Owner

Adaptive role. Maintains Product Backlog, develops User Stories, and acts as Voice of the Customer.

Project Manager

Person assigned by organization to lead the team.  Accountable for project objectives.

Quality

Provide a product or service that conforms to requirements and is fit for use.

Refinement

The act of updating the Product Backlog based on changing product requirements.

Retrospective

Ceremony conducted at end of each Sprint to determine what went well, what should the team change, and what is one change the team will pursue during the next Sprint.

SAFe

Scaled Agile Framework. A set of organization and workflow patterns intended to guide enterprises in scaling lean and agile practices.

Scrum

A popular form of agile used by the majority of agile practitioners.

Scrum Master

Adaptive role. Trains and coaches development team.  Ensures all agile processes are adhered to.

Self-Organize

Ability of a team to organize and take the right actions without the need for management direction.

Sprint/Iteration

A timed period where an adaptive or agile project is implemented. Generally, time boxed at 15 or 30 days.

Sprint Backlog

A list of tasks to support a User Story developed by a Scrum development team.

Sprint Demo/Review

Ceremony where the Product owner presents the functionality developed by the team during a Sprint and receives feedback and acceptance.

Sprint Planning

The Scrum team determines which user Stories will be accomplished during a Sprint. Sprint backlog is developed to execute the User stories.

User Stories

A requirement defined by role, need, and value developed by a Product Owner.

Velocity

The amount of work a team can complete in a given Sprint.